\pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\f0\b0\i0\ulnone\fs28\fc0\cf0 Q. When I reboot after performing:\
\
\b
\f1\b0\fs24 niload -d hosts / < /etc/hosts
\f0\fs28 \
\
why does the NetInfo server display the following message? \
\
\f1\fs24 cannot find parent NetInfo server, still looking...\
Press 'c' to continue boot without parent server.\
See your system administrator if you need help.\
\f0\fs28 \
A. During the
\b niload -d
\b0 command the entry for the local host in the NetInfo root domain got deleted, or perhaps a new entry was created without the
\b serves
\b0 property. In either case, without the
\b serves
\b0 property, a machine can't find its parent server.\
\
\b niload -d
\b0 deletes entries that are in the directory but not in the input (which in this case is \
/etc/hosts). Thus either the machine's entry is completely lost (if the corresponding entry is not in /etc/hosts), or else the machine's entry is overwritten by the new entry, deleting the
\b serves
\b0 property in the process. (
\b niload
\b0 is not capable of adding properties other than the standard Unix ones, which are
\b ip_address
\b0 and
\b name
\b0 in this case.)\
\
There are two different procedures for fixing the problem, depending on whether the
\b serves
\b0 property got corrupted on a NetInfo
\b client
\b0 or on a
\b server.\
\
1. If the Machine is a Client:\
\b0 \
The procedure to fix the problem is easier in this case, since the root domain can be accessed through NetInfoManager. Run NetInfoManager on the NetInfo server and add the missing
\b machines
\b0 subdirectory or the missing
\b serves
\b0 property (of the form
\b\i hostname
\i0 /local
\b0 ) to the root domain:\
\
\fi-980\li980 • Launch NetInfoManager.\
• Open the / (root) domain.\
• Edit Properties for
\i hostname
\i0 , where
\i hostname
\i0 is the name of your client (see following section if there is no entry for
\i hostname)
\i0 .\
• Make a
\b serves
\b0 property.\
• Change newValue of the
\b serves
\b0 property to
\i hostname
\i0 /local.\
• Reboot
\i hostname
\i0 .\
\fi0\li0 \
If there is no
\b machines
\b0 entry for
\i hostname
\i0 , create one:\
\
\fi-980\li980 • Create a new
\b machines
\b0 subdirectory for
\i hostname
\i0 .\
• Change the
\b machines
\b0 subdirectory from newValue to
\i hostname
\i0 .\
• Edit Properties for
\i hostname
\i0 .\
• an
\b ip_address
\b0 property with a value of the form
\i xxx.yy.zzz.aaa
\i0 , replacing
\i xxx.yy.zzz.aaa
\i0 with the correct ip-address.\
• a
\b serves
\b0 property with the value
\i hostname
\i0 /local\
• Reboot
\i hostname
\i0 .\
\fi0\li0 \
\
\b 2. If the Machine is a Server:\
\b0 \
If the machine is the server, the procedure is a little more involved:\
\
\fi-980\li980 • Boot the machine, and when you get the error message, type "c" to continue. Once the machine is up, log in. Open a Shell or Terminal and
\b su
\b0 to root if you are not already logged in as root. \
